Skip to content

build: remove flowing code and vaadin pre-release repositories AND ci: upgrade Vaadin to 25.0.3 #106

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Merged
paodb merged 6 commits into from
Jan 23, 2026
Merged

build: remove flowing code and vaadin pre-release repositories AND ci: upgrade Vaadin to 25.0.3 #106

paodb merged 6 commits into from
Jan 23, 2026

Conversation

@javier-godoy
Copy link
Member

@javier-godoy javier-godoy commented Jan 23, 2026 •
edited by coderabbitai bot
Loading

Summary by CodeRabbit

Release Notes

  • Chores
    • Updated Vaadin framework from beta to stable release version 25.0.3
    • Upgraded Jetty, testing dependencies, and related libraries to latest stable versions
    • Removed unused repository configurations

✏️ Tip: You can customize this high-level summary in your review settings.

@javier-godoy javier-godoy requested a review from paodb January 23, 2026 14:27
@coderabbitai
Copy link

coderabbitai bot commented Jan 23, 2026 •
edited
Loading

Walkthrough

Updated Maven configuration in pom.xml to bump multiple dependency versions (Jetty 11.0.12→11.0.26, commons-demo 4.0.0→5.1.0, webdrivermanager 3.8.1→6.3.2, Vaadin 25.0.0-beta2→25.0.3), removed FlowingCode repository declarations, and replaced a test dependency with an optional Vaadin dev dependency in the v25 profile.

Changes

Cohort / File(s) Summary
Maven Configuration
pom.xml		 • Updated jetty.version property from 11.0.12 to 11.0.26
• Removed FlowingCode Releases and FlowingCode Snapshots repository declarations
• Bumped com.flowingcode.vaadin.addons.demo:commons-demo from 4.0.0 to 5.1.0 (test scope)
• Bumped io.github.bonigarcia:webdrivermanager from 3.8.1 to 6.3.2 (test scope)
• Updated vaadin.version from 25.0.0-beta2 to 25.0.3
• In v25 profile: replaced commons-demo:4.4.0-SNAPSHOT (test) with vaadin-dev (optional); removed prerelease repository sections

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~15 minutes

🚥 Pre-merge checks | ✅ 3
✅ Passed checks (3 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title directly addresses the two main changes: removing FlowingCode and Vaadin pre-release repositories, and upgrading Vaadin to version 25.0.3, which are clearly reflected in the pom.xml modifications.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

@sonarqubecloud
Copy link

sonarqubecloud bot commented Jan 23, 2026

Quality Gate Passed Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

@paodb paodb merged commit 60dd51b into master Jan 23, 2026
4 checks passed
@github-project-automation github-project-automation bot moved this from To Do to Pending release in Flowing Code Addons Jan 23, 2026
@paodb paodb deleted the vaadin-25 branch January 23, 2026 14:46
This was referenced Jan 23, 2026
Closed
Closed
@paodb paodb moved this from Pending release to Done in Flowing Code Addons Feb 2, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@paodb paodb paodb approved these changes

Assignees

No one assigned

Labels

None yet

Projects

Flowing Code Addons
Status: Done

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

2 participants

@javier-godoy @paodb